Document management system, document management method, program and storage medium

ABSTRACT

In a document management system according to the present invention, which is used for registering and managing a document in a database of a relational database server, a judgment is made as to whether or not a capacity of the database has reached a predetermined limited capacity, and when it is judged that the predetermined limited capacity has been reached, an identifier indicating an editing-inhibited state is added to the database, to inhibit all editing actions to the database, thereby achieving the user-friendly system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a document management system forregistering and managing a document in a relational database.

2. Related Background Art

Conventionally, in a document management system using a relationaldatabase, in a case where a capacity of the database exceeds a limitedrecordable capacity, when a user tries to register a document, thedocument management system requires the user to delete a portion of thedata being saved.

In the conventional document management system, when a plurality ofusers share the database, there were cases where some user required todelete data would delete the data at his/her own discretion, causingconfusion among the users.

Further, at the time when the user gives an instruction to registerdata, he/she would first learn that the database is in a state in whicha document cannot be registered, and thus the system was difficult touse.

SUMMARY OF THE INVENTION

According to the present invention, for example in a case where adatabase capacity has reached a predetermined size, editing processessuch as registering, deleting and replacing data can no longer beperformed, thereby achieving the user-friendly system.

According to the present invention, there is provided a documentmanagement system for registering and managing a document in a databaseof a relational database server, the system including:

-   -   judging means for judging whether or not a capacity of the        database has reached a predetermined limited capacity; and    -   inhibiting means for adding to the database an identifier        indicating an editing-inhibited state so as to inhibit all        editing actions to the database, when the judging means judges        that the capacity of the database has reached the predetermined        limited capacity.

According to the present invention, there is provided a documentmanagement method for registering and managing a document in a databaseof a relational database server, the method including:

-   -   judging whether or not a capacity of the database has reached a        predetermined limited capacity; and    -   performing inhibition while adding to the database an identifier        indicating an editing-inhibited state so as to inhibit all        editing actions to the database, when that the capacity of the        database has reached the predetermined limited capacity is        judged in the judging.

Other features and advantages of the patent invention will be apparentfrom the following description taken in conjunction with theaccompanying drawings, in which like reference characters designate thesame or similar parts throughout the figure thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the specification, illustrate embodiments of the invention and,together with the description, serve to explain the principles of theinvention.

FIG. 1 shows a configuration of a document management system;

FIG. 2 is a flowchart of processes executed by a document managingclient;

FIG. 3 is a flowchart of a login process;

FIG. 4 is a flowchart of a document registration process; and

FIG. 5 shows anther embodiment at a time when an instruction is givenfor an editing process such as registering, deleting or replacing adocument.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1

FIG. 1 shows a configuration of a document management system of thisembodiment. In accordance with this embodiment, a document managingserver 1, a relational database server 2, document managing clients 3and 4, and the like are connected to an Ethernet (R) 5. Here, thedocument managing server 1 is configured such that it can performcommunications with the relational database server 2 and the documentclients 3 and 4 via the network. Then, when there is a process requestfrom the document managing client 3 or 4, the document managing server 1can interpret the content of the request and can read/write documentdata with respect to the relational database server.

The relational database server 2 stores a database that is used in thepresent invention.

The document managing clients 3 and 4 can give the document managingserver 1 instructions to register and read the document data.

Note that, the document managing server, the relational database server,and the document managing clients of this embodiment are realized bymeans of a program operating on a computer. However, the computer may beconfigured with a single device, or may be configured with a pluralityof devices. Further, the computer is constituted by: a CPU forperforming overall control of this apparatus according to a documentmanagement control program which corresponds to a flowchart describedbelow; a RAM, a ROM, a hard disk, or a removable storage medium used asstorage means; a display for performing a display; a keyboard and apointing device for transmitting instructions from a user; a networkinterface for communications with the external, and the like. Note that,the document management control program used in this embodiment may bestored in the ROM, the hard disk, or other such internal storage media,it may also be stored on a Floppy (R) disk, a CD-ROM, or other suchexternal storage media to be read and executed as needed, and it mayalso be received from an external device via the network to be executed.Further, in accordance with this embodiment, the document managingserver and the relational database server operate on separate computers,but they may also be configured to operate on the same computer.

FIG. 2 is a flowchart for explaining processes executed by the documentmanaging client.

Step S2001 is an initialization process for building a screen and thelike, which is performed at a time when the document managing client isbooted.

Step S2010 is a branching process for interpreting an input operation bythe user, and depending on the content of the operation, branching theprocessing into steps corresponding to operations.

Step S2020 is a process performed at a time when the user performs adatabase login process. Detailed content of this process is explainedbelow using FIG. 3.

Step S2030 is a process performed in a case where the user performs adocument registration process. The document registration process refersto an editing process, in which a file of a file system browsable fromthe computer where the document management client program is operatingis registered into the relational database server 2 via the documentmanaging server 1. Detailed content of this editing process is explainedbelow using FIG. 4.

Step S2040 is a process for performing editing (registration, deletion,replacement, and other such alterations) to document information whichis displayed by the user giving an instruction to display the documentinformation that is stored in the database in correspondence with thedocument. The document information is displayed per document, and in acase where the document information has been edited, the edited documentinformation is written back into the database.

Note that, in a case where the database has already changed to anediting-inhibited state, when the document information is displayed, anedit menu of a user interface is displayed so that the user understandsthat editing is not possible (for example, a menu item for performingthe editing processes is grayed out to clearly indicate that it cannotbe used). The editing processes for registration, deletion, replacement,and the like in step S2030 and step S2040 cannot be executed in thedatabase.

Step S2050 is a process performed when the user has executed a documentsearch operation. Here, when the document search instruction is receivedfrom the user, a document search screen is displayed, and a documentsearch can be performed. The document search screen is configured suchthat the document information can be inputted as search information. Asa result of the search, if documents are found, a list of the documentsfound by the search is displayed on a search results screen. As a resultof the search, if documents are not found, a message indicating this isdisplayed, and the control is returned to the document search screen.

Step S2060 is a process performed when the user performs a closingprocess. A process for disconnection from the connected database (alogout process) is performed, and the program is ended.

FIG. 3 is a flowchart for explaining a process at a time when the userperforms the login operation.

Step S3001 is a process for requiring the user to input a user name anda password for connecting to the database which is to be logged into.

In step S3010, a verification process is performed for verifying whetheror not the user name and the password inputted at step S3001 can be usedto perform the connection to the database. If it is judged that theconnection is made successfully, the processing advances to step S3020,and if the connecting cannot be achieved, then a message indicating thatthe verification failed is displayed, and the processing returns againto step S3001, and the user is asked to re-input the user name and thepassword.

At step S3020, a judgment is made as to whether or not the database isin the editing-inhibited state, and the processing branches offdepending on the result of the judgment. In a case where the database isnot in the editing-inhibited state, the login processing ends, and thedatabase browsing process and the editing processes such as registering,deleting and replacing documents become executable. On the other hand,in a case where the database is in the editing-inhibited state, theediting processes such as registering, deleting and replacing documentsbecome unexecutable, and the processing advances to step S3021. Notethat, the judgment of whether or not the database is in theediting-inhibited state is performed based on an editing-identificationidentifier, which is saved in the database. Note that, in the case wherethe database is already in the editing-inhibited state, the display tothat effect is made on the user interface of the client such that theuser understands that the editing cannot be performed (for example, themenu item for performing the editing process is grayed out to clearlyindicate that it cannot be used).

At step S3021, a message display flag is confirmed, and in a case wherethe message display flag is set ON, the processing advances to stepS3022, and in a case where it is not set ON, the processing ends. Themessage display flag is saved in a non-volatile storage area andmaintained even after the program is ended, and it can also bereferenced at subsequent times when the program is loaded. In itsinitial state, the flag is set so as to be displayed (the ON state).

At step S3022, a message for informing the user that the database is inthe editing-inhibited state is displayed on the message display screen.At this time, a check box as to whether or not the same message shouldbe displayed each time the editing action is to be performed at thesubsequent time forward is provided in the message display screen.

At step S3023, the processing branches off depending on whether or notthe user selected at step S3022 the check box as to whether or not todisplay the same massage at the subsequent time forward. In a case wherethe same message is to be displayed at the subsequent time forward, theprocess ends, and in the case where the user selected the check boxindicating that display of the message at the subsequent time forward isunnecessary, the processing advances to step S3024.

At step S3024, the message display flag is set OFF (not to display themessage), and the message display flag is saved.

FIG. 4 shows a process performed by the document managing server 1 at atime when the user performs a document registration process operation.The target document of the registration in the file system of the clienthas been indicated by the user before performing the process.

Step S4010 is a process for confirming whether or not to save theindicated document in the file system of the client. If the document isnot to be saved, a message indicating this is displayed at step S4050,and the process ends.

At step S4020, the designated document is obtained from the documentmanaging client, and a process for registering the document into thedatabase of the database server is performed.

At step S4030, the capacity of the disk on which the database is storedis confirmed, and in a case where there is a remaining capacity, theprocessing advances to step S4032, and in a case where there is nocapacity remaining, the processing advances to step S4035.

At step S4032, it is judged whether or not the database capacity hasreached a predetermined limited capacity, and in a case where thepredetermined limited capacity has been reached, the process advances tostep S4035, and in a case where the predetermined capacity has not beenreached, the processing ends. Note that, the predetermined limitedcapacity is a fixed value predetermined based on the capacity allowablefor the document managing program of this embodiment.

At step S4035, the editing-identification identifier for indicating theediting-inhibited state is saved in the database so as to put thedatabase in the editing-inhibited state.

At step S4040, the message display flag is confirmed, and in the casewhere the message display flag is ON, the processing advances to stepS4042, and in the case where the message display flag is OFF, theprocess ends.

At step S4042, a control is performed for a message display in thedisplay screen of the document managing client, indicating that thedatabase is set in the editing-inhibited state. Note that, when theclient receives this message, the control is performed such that theuser understands that the editing cannot be performed on the userinterface of the client (for example, the menu item for performing theediting process is grayed out to clearly indicate that it cannot beused). At this time, in the message display screen there is provided acheck box as to whether or not to display the same message each time theediting action is to be performed at the subsequent time forward.

Step S4045 is a process through which the processing branches offdepending on whether or not the user selected at step S4042 the checkbox to display the same message each time the editing action is to beperformed at the subsequent time forward. In the case where the messageis to be displayed at the subsequent time forward, the process ends, andin the case where the message is not to be displayed at the subsequenttimes, the process advances to step S4047, and the message display flagis set not to display the message, and this condition is saved.

Embodiment 2

In accordance with Embodiment 1 above, the limited capacity used in stepS4032 in FIG. 4 to confirm whether or not the capacity of the databasereaches the predetermined limited capacity is determined as thepredetermined fixed value. However, the limited capacity may also be setat a value desired by the user. In such a case, a user interface programfor setting the limited capacity before the document registrationprocess is provided separately.

Embodiment 3

In accordance with Embodiment 1, when the editing-identificationidentifier is applied to the database and the database enters theediting-inhibited state, the menu items for performing the editingprocesses (registration, deletion, replacement, alteration, etc.) aregrayed out on the client side, to prevent all editing actions. Inaccordance with Embodiment 3, in addition to the characteristics ofEmbodiment 1, a description will be given of a case in which, when theinstruction for editing is sent even though the database is in theediting-inhibited state and the display shows that the editing actionscannot be performed, a warning message indicating the editing-inhibitedstate is displayed, and the program is ended without performing theediting process. FIG. 5 is a flowchart indicating a process of thedocument managing server according to this embodiment.

When an editing instruction for registration, deletion, replacement,alteration or the like is given, at step S5010, it is judged whether ornot the editing-identification identifier has been applied to thedatabase, and in a case where it is judged that it has been applied, atstep S5120, a control is performed such that the client displays thewarning message that the database is in the editing-inhibited state, andthe editing process is not performed.

On the other hand, in a case where it is judged that theediting-identification identifier has not been applied to the database,if the editing instruction is for the registration process (step S5020),the same processing as in FIG. 4 is executed at step S5030. In a casewhere another editing process for deletion, replacement, alteration orthe like has been instructed, at step S5040, the editing process isexecuted. After that, in a case where it is judged at step S5050 andstep S5060 that the disk capacity or the database capacity has exceededthe predetermined limited value, at step S5070, theediting-identification identifier indicating the editing-inhibited stateis saved in the database so that the database enters theediting-inhibited state. Since the processes of steps S5080 throughS5110 are similar to the processes of steps S4040 through S4047 in FIG.4, explanations thereof are omitted.

As described above using Embodiments 1 through 3, in accordance with thepresent invention, in the case where the database capacity has exceededthe predetermined limited capacity, all the editing actions such aswriting and deleting to/from the database are inhibited, wherebyconfusion of the user can be prevented.

Further, in the case where the editing actions are inhibited, thedisplay to that effect is made while the edit menu is grayed out, forexample, whereby the user can easily distinguish whether or not thedatabase is allowed for the editing action, before performing editinginstruction.

1. A document management system for registering and managing a documentin a database of a relational database server in response to a client'srequest, said system comprising: a storage medium that stores thedatabase; judging means for judging whether or not a capacity of thedatabase has reached a predetermined limited capacity; and inhibitingmeans for adding to the database an identifier indicating that thedatabase is in an editing-inhibited state and notifying the client thatall editing actions, including deletion by the client, to all documentsregistered in the database are inhibited, when said judging means judgesthat the capacity of the database has reached the predetermined limitedcapacity, wherein the editing actions, including deletion by the client,to all documents registered in the database are not inhibited when saidjudging means judges that the capacity of the database has not reachedthe predetermined limited capacity, and wherein the editing actionsinclude at least the registration and deletion of the document in thedatabase, and registration and deletion are inhibited if the editingactions are inhibited, thereby preventing any one of the documentsregistered in the database from being deleted.
 2. A document managementsystem according to claim 1, wherein, when the identifier indicating theediting-inhibited state is added to the database, a control is performedto display a message indicating that the database is in theediting-inhibited state.
 3. A document management system according toclaim 1, wherein, when the client connects to the database added withthe identifier indicating the editing-inhibited state, a control isperformed to display a message indicating that the database is in theediting-inhibited state.
 4. A document management system according toclaim 1, wherein a user interface of the client is modified so that astate in which the database added with the identifier indicating theediting-inhibited state cannot be edited is recognizable.
 5. A documentmanagement system according to claim 1, wherein the predeterminedlimited capacity can be modified by a user.
 6. A document managementsystem according to claim 1, wherein the predetermined limited capacityis determined according to a disk capacity of the database and anallowable capacity of a management program of the database.
 7. Adocument management system according to claim 1, wherein the editingactions by all users to the database further include replacement of thedocument in the database.
 8. A document management method forregistering and managing a document in a database of a relationaldatabase server in response to a client's request, said methodcomprising: judging whether or not a capacity of the database hasreached a predetermined limited capacity; and performing inhibitionwhile adding to the database an identifier indicating that the databaseis in an editing-inhibited state and notifying the client that allediting actions, including deletion by the client, to all documentsregistered in the database are inhibited, when said judging step judgesthat the capacity of the database has reached the predetermined limitedcapacity, wherein the editing actions, including deletion by the client,to all documents registered in the database are not inhibited when saidjudging step judges that the capacity of the database has not reachedthe predetermined limited capacity, and wherein the editing actionsinclude at least the registration and deletion of the document in thedatabase, and registration and deletion are inhibited if the editingactions are inhibited, thereby preventing any one of the documentsregistered in the database from being deleted.
 9. A document managementmethod according to claim 8, wherein, when the identifier indicating theediting-inhibited state is added to the database, a control is performedto display a message indicating that the database is in theediting-inhibited state.
 10. A document management method according toclaim 8, wherein, when the client connects to the database added withthe identifier indicating the editing-inhibited state, a control isperformed to display a message indicating that the database is in theediting-inhibited state.
 11. A document management method according toclaim 8, wherein a user interface of the client is modified so that astate in which the database added with the identifier indicating theediting-inhibited state cannot be edited is recognizable.
 12. A documentmanagement method according to claim 8, wherein the predeterminedlimited capacity can be modified by a user.
 13. A document managementmethod according to claim 8, wherein the predetermined limited capacityis determined according to a disk capacity of the database and anallowable capacity of a management program of the database.
 14. Adocument management method according to claim 8, wherein the editingactions by all users to the database further include replacement of thedocument in the database.
 15. A computer-executable program stored on acomputer-readable memory medium, said program for making a computerregister and manage a document in a database of a relational databaseserver in response to a client's request, said program comprising aprogram code for making the computer execute: judging whether or not acapacity of the database has reached a predetermined limited capacity;and performing inhibition while adding to the database an identifierindicating that the database in is an editing-inhibited state andnotifying the client that all editing actions, including deletion by theclient, to all documents registered in the database are inhibited, whensaid judging step judges that the capacity of the database has reachedthe predetermined limited capacity, wherein the editing actions,including deletion by the client, to all documents registered in thedatabase are not inhibited when said judging step judges that thecapacity of the database has not reached the predetermined limitedcapacity, and wherein the editing actions include at least theregistration and deletion of the document in the database, andregistration and deletion are inhibited if the editing actions areinhibited, thereby preventing any one of the documents registered in thedatabase from being deleted.
 16. A computer-executable program accordingto claim 15, comprising a program code for, when the identifierindicating the editing-inhibited state is added to the database,performing a control to display a message indicating that the databaseis in the editing-inhibited state.
 17. A computer-executable programaccording to claim 15, further comprising a program code for, when theclient connects to the database added with the identifier indicating theediting-inhibited state, performing a control to display a messageindicating that the database is in the editing-inhibited state.
 18. Acomputer-executable program according to claim 15, further comprising aprogram code for performing a control to modify a user interface of theclient so that a state in which the database added with the identifierindicating the editing-inhibited state cannot be edited is recognizable.19. A computer-executable program according to claim 15, wherein theediting actions by all users to the database further include replacementof the document in the database.
 20. A computer readable storage mediumstoring the computer-executable program according to claim
 15. 21. Adocument management system according to claim 1, wherein the databasedoes not accept all editing actions to all documents from all clientswhich request connection to the database, when the identifier indicatesthe editing-inhibited state.
 22. A document management method accordingto claim 8, wherein the database does not accept all editing actions toall documents from all clients which request connection to the database,when the identifier indicates the editing-inhibited state.
 23. Acomputer-executable program according to claim 15, wherein the databasedoes not accept all editing actions to all documents from all clientswhich request connection to the database, when the identifier indicatesthe editing-inhibited state.
 24. A document management system accordingto claim 1, wherein said inhibiting means adds the identifier to thedatabase so as to inhibit all editing actions by all users to thedatabase, thereby preventing any one of the documents in the databasefrom being deleted.
 25. A document management method according to claim8, wherein said performing inhibition step adds the identifier to thedatabase so as to inhibit all editing actions by all users to thedatabase, thereby preventing any one of the documents in the databasefrom being deleted.
 26. A computer-executable program according to claim15, wherein said performing inhibition step adds the identifier to thedatabase so as to inhibit all editing actions by all users to thedatabase, thereby preventing any one of the documents in the databasefrom being deleted.
 27. A document management server for registering andmanaging a document in a database, said server comprising: a storagemedium that stores the database; registration means for obtaining adocument from a document management client and registering the obtaineddocument in the database; judging means for judging whether or not acapacity of the database has reached a predetermined limited capacitydue to the registration of the obtained document by said registrationmeans; and control means for controlling the database to store anidentifier indicating that the database is in an editing-inhibited stateand notifying the document management client that all editing actions,including deletion by the document management client, to all documentsregistered in the database are inhibited, when said judging means judgesthat the capacity of the database has reached the predetermined limitedcapacity, wherein the editing actions, including deletion by thedocument management client, to all documents registered in the databaseare not inhibited when said judging means judges that the capacity ofthe database has not reached the predetermined limited capacity, andwherein the editing actions include at least the registration anddeletion of the document in the database, and registration and deletionare inhibited if the editing actions are inhibited, thereby preventingany one of the documents registered in the database from being deleted.28. A document management method for registering and managing a documentin a database of a relational database server, said method comprising: aregistration step of obtaining a document from a document managementclient and registering the obtained document in the database; a judgingstep of judging whether or not a capacity of the database has reached apredetermined limited capacity due to the registration of the obtaineddocument in said registration step; and a controlling step ofcontrolling the database to store an identifier indicating that thedatabase is in an editing-inhibited state and notifying the documentmanagement client that all editing actions, including deletion by thedocument management client, to all documents registered in the databaseare inhibited, when said judging step judges that the capacity of thedatabase has reached the predetermined limited capacity, wherein theediting actions, including deletion by the document management client,to all documents registered in the database are not inhibited when saidjudging step judges that the capacity of the database has not reachedthe predetermined limited capacity, and wherein the editing actionsinclude at least the registration and deletion of the document in thedatabase, and registration and deletion are inhibited if the editingactions are inhibited, thereby preventing any one of the documentsregistered in the database from being deleted.
 29. A computer-executableprogram stored on a computer-readable memory medium, said program formaking a computer register and manage a document in a database of arelational database server, said program comprising a program code formaking the computer execute: a registration step of obtaining a documentfrom a document management client and registering the obtained documentin the database; a judging step of judging whether or not a capacity ofthe database has reached a predetermined limited capacity due to theregistration of the obtained document in said registration step; and acontrolling step of controlling the database to store an identifierindicating that the database is in an editing-inhibited state andnotifying the document management client that all editing actions,including deletion by the document management client, to all documentsregistered in the database are inhibited, when said judging step judgesthat the capacity of the database has reached the predetermined limitedcapacity, wherein the editing actions are not inhibited when saidjudging step judges that the capacity of the database has not reachedthe predetermined limited capacity, and wherein the editing actionsinclude at least the registration and deletion of the document in thedatabase, and registration and deletion are inhibited if the editingactions are inhibited, thereby preventing any one of the documentsregistered in the database from being deleted.
 30. A document managementsystem according to claim 1, wherein said inhibiting means notifies theclient that all editing actions, including deletion by the client, toall documents registered in the database are inhibited, so as to causethe client to display a message indicating contents of the notification.31. A document management server according to claim 27, wherein saidcontrol means notifies the document management client that all editingactions, including deletion by the document management client, to alldocuments registered in the database are inhibited, so as to cause thedocument management client to display a message indicating contents ofthe notification.
 32. A document management system comprising: adatabase for storing documents; a storage medium that stores thedatabase; judging means for judging whether or not a capacity of thedatabase has reached a predetermined limited capacity, when aregistration instruction of a document from a user of a client isperformed; and control means for controlling the client to displayinformation indicating that the user of the client cannot request saiddocument management system to delete any one of the documents stored insaid database, when said judging means judges that the capacity of thedatabase has reached the predetermined limited capacity, wherein theuser of the client can request said document management system to deleteany one of the documents stored in said database, when said judgingmeans judges that the capacity of the database has not reached thepredetermined limited capacity.
 33. A document management systemaccording to claim 32, wherein if the user of the client executes alogout process and then another user executes a login process, theclient is notified, based on an editing-inhibition identifier saved inthe database, that editing actions are inhibited.
 34. A documentmanagement system according to claim 33, wherein document search isallowed even if document deletion is inhibited, and wherein if the userexecutes a logout process, the client is disconnected from the database.35. A document management method according to claim 8, wherein saidperforming inhibition step notifies the client that all editing actions,including deletion by the client, to all documents registered in thedatabase are inhibited, so as to cause the client to display a messageindicating contents of the notification.
 36. A document managementmethod according to claim 28, wherein said control step notifies thedocument management client that all editing actions, including deletionby the document management client, to all documents registered in thedatabase are inhibited, so as to cause the document management client todisplay a message indicating contents of the notification.
 37. Adocument management method comprising: storing documents in a databaseof a document management system; judging whether or not a capacity ofthe database has reached a predetermined limited capacity, when aregistration instruction of a document from a user of a client isperformed; and controlling the client to display information indicatingthat the user of the client cannot request the document managementsystem to delete any one of the documents stored in said database, whensaid judging step judges that the capacity of the database has reachedthe predetermined limited capacity, wherein the user of the client canrequest said document management system to delete any one of thedocuments stored in said database, when said judging step judges thatthe capacity of the database has not reached the predetermined limitedcapacity.
 38. A document management method according to claim 37,wherein if the user of the client executes a logout process and thenanother user executes a login process, the client is notified, based onan editing-inhibition identifier saved in the database, that editingactions are inhibited.
 39. A document management method according toclaim 38, wherein document search is allowed even if document deletionis inhibited, and wherein if the user executes a logout process, theclient is disconnected from the database.
 40. A computer-executableprogram according to claim 15, wherein said performing inhibiting stepnotifies the client that all editing actions, including deletion by theclient, to all documents registered in the database are inhibited, so asto cause the client to display a message indicating contents of thenotification.
 41. A computer-executable program according to claim 29,wherein said controlling step notifies the document management clientthat all editing actions, including deletion by the document managementclient, to all documents registered in the database are inhibited, so asto cause the document management client to display a message indicatingcontents of the notification.
 42. A computer-executable program storedon a computer-readable memory medium, said program for making a computerregister and manage a document in a database of a relational databaseserver, said program comprising a program code for making the computerexecute: storing documents in a database of a document managementsystem; judging whether or not a capacity of the database has reached apredetermined limited capacity, when a registration instruction of adocument from a user of a client is performed; and controlling theclient to display information indicating that the user of the clientcannot request said document management system to delete any one of thedocuments stored in said database, when said judging means judges thatthe capacity of the database has reached the predetermined limitedcapacity, wherein the user of the client can request said documentmanagement system to delete any one of the documents stored in saiddatabase, when said judging step judges that the capacity of thedatabase has not reached the predetermined limited capacity.
 43. Acomputer-executable program according to claim 42, wherein if the userof the client executes a logout process and then another user executes alogin process, the client is notified, based on an editing-inhibitionidentifier saved in the database, that editing actions are inhibited.44. A computer-executable program according to claim 43, whereindocument search is allowed even if document deletion is inhibited, andwherein if the user executes a logout process, the client isdisconnected from the database.